Memory system having high data transfer efficiency and host controller

ABSTRACT

According to one embodiment, the host controller includes a register set to issue command, and a direct memory access (DMA) unit and accesses a system memory and a device. First, second, third and fourth descriptors are stored in the system memory. The first descriptor includes a set of a plurality of pointers indicating a plurality of second descriptors. Each of the second descriptors comprises the third descriptor and fourth descriptor. The third descriptor includes a command number, etc. The fourth descriptor includes information indicating addresses and sizes of a plurality of data arranged in the system memory. The DMA unit sets, in the register set, the contents of the third descriptor forming the second descriptor, from the head of the first descriptor as a start point, and transfers data between the system memory and the host controller in accordance with the contents of the fourth descriptor.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of and claims the benefit of priority under 35 U.S.C. §120 from U.S. Ser. No. 13/052,147 filed Mar. 21, 2011, and claims the benefit of priority under 35 U.S.C. §119 from Japanese Patent Application No. 2010-212721 filed Sep. 22, 2010, the entire contents of each of which are incorporated herein by reference.

FIELD

Embodiments described herein relate generally to a host controller and memory system to be applied to, e.g., a SD™ card, and supporting advanced direct memory access (ADMA).

BACKGROUND

Recently, SD cards such as SD memory cards are widely used in, e.g., cell phones and digital still cameras as host devices. This SD card is connected to a host device via a host controller, and the host controller controls data transmission between the host device and SD memory card.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic view showing the arrangement of a memory system according to an embodiment;

FIG. 2 is a schematic view showing the memory maps of a system memory and memory card;

FIG. 3 is a view showing the structure of a descriptor according to the embodiment;

FIG. 4 is a schematic view showing the arrangement of ADMA shown in FIG. 1; and

FIG. 5 is a flowchart showing the operation of ADMA.

DETAILED DESCRIPTION

A system memory installed in a host device is managed by paging. Therefore, data in the system memory is fragmentarily managed page-by-page.

To efficiently perform data read/write to a memory card, a host controller supports DMA algorithm capable of data transfer managed page-by-page. That is, data fragmented in the system memory can be transferred by DMA by using a descriptor as a data transfer list.

Unfortunately, conventional DMA algorithm generates an interrupt in order to generate a new system address in the boundary between pages. This disturbs the operation of a CPU. ADMA has been developed in order to eliminate this problem.

ADMA has a function of transferring data to fragmented data areas in the system memory by paging, in accordance with one read/write command of an SD card. Accordingly, ADMA controls data transfer between the host controller and system memory without any interrupt to the CPU by loading the descriptor in the system memory. A host driver controls the issue of a command to the memory card by setting a register set in the host controller, thereby controlling data transfer between the host controller and memory card, and interruption to the CPU has been used. This method poses no problem when the bus performance is low as in a conventional memory.

As the bus performance improves and high-speed data transfer becomes possible in recent years, however, the processing of the host driver generates an overhead. Since it is not always possible to continuously use the area of the memory card, a memory command must be divided into a plurality of memory commands. To control command issue to the memory card by the host driver, the host driver must be executed by causing the host CPU to generate an interrupt midway along data transfer. Therefore, it takes a certain time to respond to the interrupt. This deteriorates the performance because of the influence of the waiting time of the driver processing even when using a high-speed bus.

Accordingly, demands have arisen for a method of efficiently performing data transfer by making it possible to execute, by DMA, the processing requiring the host driver during data transfer.

Embodiment

In general, according to one embodiment, a memory system includes a host controller and DMA unit. The host controller includes a register set configured to control command issue to a device, and a direct memory access (DMA) unit configured to access a system memory, and controls transfer between the system memory and the device. First, second, third and fourth descriptors are stored in the system memory. The first descriptor includes a set of a plurality of pointers indicating a plurality of second descriptors. Each of the second descriptors comprises the third descriptor and fourth descriptor. The third descriptor includes a command number, a command operation mode, and an argument as information necessary to issue a command to the device, and a block length and the number of blocks as information necessary for data transfer. The fourth descriptor includes information indicating addresses and sizes of a plurality of data arranged in the system memory. The ADMA unit sets, in the register set, the contents of the third descriptor forming the second descriptor, from the head of the first descriptor as a start point, and loads and transfers data from the system memory in accordance with the contents of the fourth descriptor.

The embodiment will be explained below with reference to the accompanying drawing. The ADMA described below is an ADMA improved by the embodiment.

FIG. 1 schematically shows the memory system according to this embodiment.

This embodiment makes it possible to issue SD commands by a host controller during DMA transfer by extending a descriptor capable of data transfer of a system memory, thereby reducing the overhead caused by host driver processing.

A system controller 11 shown in FIG. 1 controls interfaces with a CPU 12, system memory 13, and SD controller 14.

The system memory 13 stores a host driver 21, descriptor table 22, and data 23. An operating system (OS) secures areas required to store the host driver 21, descriptor table 22, and data 23 in the system memory 13.

The host driver 21 is a driver provided for, e.g., the SD host controller 14 and unique to the OS, and is executed by the CPU 12. The host driver 21 generates the descriptor table 22 before executing ADMA (to be described later). The descriptor table 22 is a list of information necessary for data transfer between the system memory 13 and an SD card, and is described by format which can be interpreted by the SD host controller. The structure of the descriptor table 22 will be described later. The SD host controller 14 has a function of bidirectionally transferring data between the system memory 13 and an SD card by using SD commands. The SD host controller 14 mainly includes a system bus interface circuit 31, a memory card interface circuit 32, a register set 33 including a plurality of registers, an ADMA 34, and a timer 35.

The system bus interface circuit 31 is connected to the system controller 11 via a system bus. The memory card interface circuit 32 is connectable to SD cards, e.g., an SD memory card 15 and SDIO card 16, via an SD bus interface (not shown). The SD bus interface is not limited to 4-bits type, but can be applied to e.g. UHS (Ultra High Speed)-II using LVDS (Low Voltage Differential Signaling) system. In UHS-II, commands are transferred in packet form.

The register set 33 of the SD host controller 14 is classified into a plurality of units (not shown) such as an SD command generation unit, response unit, buffer data port unit, host control unit, interrupt control unit, and ADMA unit. Information such as a command number, command mode, and argument necessary to issue an SD command and information such as a block length and the number of blocks necessary to transfer data are set in the SD command generation unit of the register set 33. When these pieces of information are set, the SD command generation unit issues a command to an SD card. The response unit in the register set 33 receives a response supplied from the SD card in response to the command.

The ADMA 34 is a circuit for transferring data between an SD card and the system memory 13 without any intervention of the CPU 12. The ADMA 34 executes data transfer in accordance with contents described in the descriptor table 22 in the system memory 13.

The timer 35 detects a timeout error. For example, the timer 35 detects a timeout error if the operation of a read command is not complete within a time set from the issue to the end of the read command. The CPU 12 is notified of this timeout error by an interrupt, and the timeout error is processed by the host driver.

FIG. 2 shows an example of the relationship between paging management of the system memory 13 and SD physical addresses. The system memory 13 is managed by paging for each small area, e.g., a 4-Kbyte area. An application executed by the host CPU 12 accesses the system memory 13 by a logical address by using a paging function managed by the host CPU 12. As indicated by a logical address system memory map, therefore, data are apparently arranged in a continuous address area. However, positions in the system memory 13 in which data are actually recorded are arbitrary, and fragmented as indicated by a physical address system memory map. These data are managed by the addresses and data lengths. The data length is variable. Also, the relationship between the physical address and logical address of data stored in the system memory 13 is managed by a page table (not shown).

On the other hand, data stored in the SD memory card 13 are managed for each page (each block) having, e.g., 512 bytes to a few Mbytes, and completely independent of the system memory 13. When data in the system memory 13 is to be stored in the SD memory card 15, therefore, as indicated by an SD physical address memory map, the data in the system memory 13 is stored by a size different from that in the system memory 13. Data in the SD memory card 15 is held in continuous memory area designated for each command and has an address designated by the command. The data length is variable and is designated by the other command.

DMA transfer directly accesses the system memory 13 by the physical address. Accordingly, DMA can be executed by forming a descriptor as a transfer list in the system memory 13.

FIG. 3 shows a descriptor according to this embodiment. This descriptor is formed in the descriptor table 22 of the system memory 13.

The descriptor of this embodiment extends a conventional descriptor and has a hierarchical structure. When using the descriptor of this embodiment, data transfer performed between the system memory 13 and SD memory card 15 by ADMA is completely executable by hardware. This obviates the need to interrupt the host CPU 12 during data transfer. Although an error processing request is notified by an interrupt, no problem arises because the probability of its occurrence is very low.

As shown in FIG. 3, a first descriptor (integrated descriptor) is a set of pointers to a plurality of second descriptors (partial descriptors).

Each second descriptor (partial descriptor) is a pair of a third descriptor (SD command descriptor) and a fourth descriptor (system memory descriptor).

The contents of the third descriptor are formed by information for issuing an SD command. That is, the contents of the third descriptor are formed by, e.g., a command number, a command mode, an argument, and a block length and the number of blocks as information necessary for data transfer. The command mode indicates, e.g., read/write. One SD command is issued by writing the third descriptor in the SD command generation unit of the register set 33 of the SD host controller 14.

The contents of the fourth descriptor (system memory descriptor) are formed by an address indicating the position of each data in the system memory 13, and a length indicating the data length, and indicate a set of a plurality of fragmented data.

Since the third descriptor corresponds to one of read/writ commands, one continuous region of the SD memory card can be designated. As shown in FIG. 2, when the memory region is divided into two or more regions, each of the regions needs the third descriptor. Therefore, the fourth descriptor corresponding to the third descriptor is programmed to the same data length as that of each third descriptor.

The first to fourth descriptors each have attribute information Att. Each attribute information Att contains, e.g., information for identifying the type of descriptor, and an end bit indicating the end position of the descriptor.

Note that the third descriptor has a format different from that of the other descriptors, so the attribute information Att may be provided in accordance with at least the first command number. Moreover, the attribute information Att may be provided with each line the same as another descriptor.

FIG. 4 shows an outline of the arrangement of the ADMA 34. The ADMA 34 includes a system address controller 34 a, data buffer 34 b, SD command controller 34 c, and buffer memory 34 d.

The system address controller 34 a manages addresses in the system memory 13. More specifically, the system address controller 34 a manages the load of the first to fourth descriptors stored in the system memory 13. That is, the start address of the first descriptor (integrated descriptor) is set in the system address controller 34 a as initial value. Thereby, the system address controller 34 a is able to read information of the first descriptor from the memory 13. Since pointers of each of the second descriptors are described in the first descriptor, the system address controller 34 a reads an address of the second descriptor designated by each of the pointers and reads the second descriptor in accordance with the address. Then, the system address controller 34 a transfers an SD command descriptor as the third descriptor forming the second descriptor to the SD command controller 34 c. In addition, the system address controller 34 a sequentially loads the address and data length of data described in the fourth descriptor forming the second descriptor. In accordance with the loaded address and data length, the system address controller 34 a reads data from the system memory 13 and transfers the data to the data buffer 34 b when performing memory write. When performing memory read, the system address controller 13 a transfers data from the data buffer 34 b to the system memory 13.

To execute these operations, the system address controller 34 a includes a plurality of registers 34 a_1 to 34 a_4, and a multiplexer (MPX) 34 a_5 for selecting output signals from these registers, in order to hold the start address of the first descriptor (integrated descriptor), the pointer of the second descriptor (partial descriptor), and the address and data length of data.

The SD command controller 34 c sequentially generates register addresses for setting values in the SD command generation unit, and sequentially sets, in the SD command generation unit of the register set 33 of the host controller 14, register setting information contained in an SD command descriptor as the third descriptor. When the setting of the registers is complete, the SD command generation unit of the register set 33 issues an SD command.

In memory write, the buffer memory 34 d loads data in the system memory 13, which is designated by the system address controller 34 a, and temporarily holds the supplied data. The data held in the data buffer 34 b is transferred to the SD memory card 15 in synchronism with an issued SD command.

In memory read, the buffer memory 34 d temporarily holds data loaded from the SD memory card 15 as a memory device in synchronism with an issued SD command, and transfers the data to a position in the system memory 13, which is designated by the system address controller 34 a.

The operation of the ADMA 34 using the extended descriptor in the above-mentioned configuration will be explained below with reference to FIG. 5.

To perform data transfer between the system memory 13 and SD memory card 15, the host driver 21 forms the extended descriptor as shown in FIG. 3 in the system memory 13. The host driver 21 sets the start address of the first descriptor in register 34 a_1 of the system address controller 34 a.

When the host driver 21 activates the ADMA 34 after that, the system address controller 34 a loads a second descriptor pointer (partial descriptor pointer) described at the head of the first descriptor (integrated descriptor), based on the start address of the first descriptor held in register 34 a_1, and holds the second descriptor pointer in register 34 a_2 (ST11).

Then, the system address controller 34 a loads a second descriptor in the location indicated by the second descriptor pointer (ST12).

The third descriptor (SD command descriptor) described at the head of the second descriptor is supplied to the SD command controller 34 c. The SD command controller 34 c writes data described in the third descriptor, in the SD command generation unit forming the register set 33 of the SD host controller 14. Consequently, the SD command generation unit issues a command to the SD memory card 15 (ST13).

Subsequently, the system address controller 34 a loads the fourth descriptor (system memory descriptor). The system address controller 34 a holds the address and data length described in the fourth descriptor, in register 34 a_3 (address) and register 34 a_4 (length), respectively. In memory write, the system address controller 34 a reads data from the system memory 13 by using the address in register 34 a_3 (address) as the start address, and transfers the read data to the data buffer 34 b. In memory read, the system address controller 34 a writes data of the data buffer 34 b in the system memory 13 by using the address in register 34 a_3 (address) as the start address (ST14).

In memory write, fragmented data supplied from the system memory 13 are combined into continuous data in the data buffer 34 b. The fourth descriptor (system memory descriptor) is made up of a plurality of data each formed by a pair of the address and data length, and the ADMA performs data transfer between the system memory and data buffer 34 b by repeating this.

After that, the ADMA transfers the data held in the data buffer 34 b to the SD memory card 15 (ST15). The ADMA accesses data in the system memory 13 in synchronism with an issued command (read/write command), and data transfer between the memory and card is executed via the data buffer 34 b by synchronizing them. The total data transfer amounts on the memory device side and system memory side must be set at the same value.

When data transfer based on one second descriptor is complete, whether the execution of the whole first descriptor is complete is determined (ST16). If the execution of the whole first descriptor is not complete, the control returns to step ST12, the next second descriptor is loaded in accordance with the partial descriptor pointer described in the first descriptor, and the above operation is executed (ST16-ST12). Each descriptor has the end bit in the above-mentioned attribute information Att, and the end position of the descriptor program can be designated by this end bit.

When the third descriptor is set in the register of the SD host controller 14 in accordance with the next second descriptor, an SD command is issued, and data is transferred in accordance with the fourth descriptor. In memory read, for example, after final data is transferred to the data buffer 34 b, it is also possible to issue the SD command of the next transmission during DMA transfer to the system memory by reading the following third descriptor. In this case, the operation speed can further be increased because the command issuing time is hidden.

On the other hand, if all the contents described in the first descriptor have been executed, the SD host controller 14 generates an ADMA completion interrupt (ST17). This allows the CPU 12 (host driver 21) to know the normal termination of the ADMA processing. If no error occurs, the host CPU 12 need not participate in transfer from the activation to the termination of the ADMA, so the host driver does not deteriorate the performance. In addition, the descriptor formation time has no influence on the transfer performance because the next descriptor can be prepared during data transfer.

A file system is instructed by the host driver to update information, when the transmission is completed. Thereby, the data transferred to the SD memory card is decided.

In the above embodiment, the host driver 21 generates the extended descriptor in the system memory 13 in order to perform data transfer between the system memory 13 and SD memory card 15. This extended descriptor includes the first descriptor as a set of pointers indicating the positions of the second descriptors. When the host driver 21 activates the ADMA 34, the ADMA 34 sequentially loads the contents of the second descriptors based on the contents of the start address of the first descriptor, and executes data transfer between the system memory 13 and SD memory card 15 in accordance with the contents of the third and fourth descriptors described in the second descriptors. Therefore, the host driver 21 does not participate in data transfer executed by the ADMA 34. This enables the ADMA 34 to perform high-speed data transfer.

Also, after being activated, the ADMA 34 generates a command by setting the third descriptor in the SD command generation unit of the register set 33, and can execute data transfer between the system memory 13 and SD memory card 15 by using hardware alone. This makes the operation speed much higher than that when the host driver 21 intervenes in the operation.

Furthermore, to operate the host driver during data transfer, the host driver is normally activated by an interrupt. Accordingly, the data transfer performance deteriorates if the interrupt response time is not negligible. However, the method of this embodiment can avoid the performance deterioration like this.

While certain embodiments have been described, these embodiments have been presented by way of example only, and are not intended to limit the scope of the inventions. Indeed, the novel embodiments described herein may be embodied in a variety of other forms; furthermore, various omissions, substitutions and changes in the form of the embodiments described herein may be made without departing from the spirit of the inventions. The accompanying claims and their equivalents are intended to cover such forms or modifications as would fall within the scope and spirit of the inventions. 

1. A memory system comprising: a host controller including a register set configured to control command issue to a device, and a direct memory access (DMA) unit configured to access a system memory, the host controller controlling data transfer between the system memory and the device; a first descriptor stored in the system memory, the first descriptor including a set of a plurality of pointers indicating a plurality of second descriptors; a third descriptor forming each of the plurality of second descriptors, the third descriptor including a command number, a command operation mode, and an argument as information necessary to issue a command to the device, and a block length and the number of blocks as information necessary for data transfer; and a fourth descriptor forming each of the plurality of second descriptors, the fourth descriptor including information indicating addresses and sizes of a plurality of data arranged in the system memory, wherein the DMA unit sets, in the register set, contents of the third descriptor forming the second descriptor, from a head of the first descriptor as a start point, and transfers data between the system memory and the host controller in accordance with contents of the fourth descriptor. 